A. Transfer MCI to cont12986

  1. Copy the MCI file into CyberArk Main Downloads and confirm the filename is exact, using no spaces or typos to avoid transfer issues.
  2. Transfer the MCI to the server: 
    scp ~/Downloads/<MCI_FILENAME> cont12986:/tmp/
  3. Connect to the server: 
    ssh cont12986
  4. Switch to the apizone user and elevate as needed: 
    su - apizone
sudo su -
    Credentials handling

    ! Password = NwQsR@404 passwords from the enterprise vault or CyberArk; avoid embedding real secrets in documentation or terminals.

  5. Verify upload under /tmp: 
    cd /tmp
ls -ltr

    i If the file is missing, re-check the source path and re-upload.

  6. Set the environment context: 
    tz-prod
    Context alias note

    i If tz-prod is an alias, verify the kubectl context via kubectl config current-context and switch if required.

B. Pod processing (direct)

  1. Find the direct pod: 
    pods | grep direct

    i Copy the pod name exactly for reuse in subsequent commands.

  2. Copy the MCI file into the pod: 
    kubectl cp /tmp/<MCI_FILENAME> <POD-NAME>:/tmp
    Troubleshooting

    ! “No such file”: check the filename and upload; “No such pod”: re-run pods | grep direct and confirm context.

  3. Enter the pod shell: 
    kubectl exec -it <POD-NAME> -- sh
  4. Inside the pod: clean temp and move the uploaded file: 
    cd /tmp
rm -rf DDO/*
rm -rf DDA/*
mv <MCI_FILENAME> DDO/

    i If “file not found”, verify the upload path and current directory.

  5. Exit the pod shell: 
    exit
  6. Monitor pod logs until processing completes: 
    logs <POD-NAME>

    i Stop log viewing with Ctrl+C once completed.

  7. Check DDA output: 
    kubectl exec -it <POD-NAME> -- sh
ls -ltr /tmp/DDA/

    i Note the DDA filename shown for retrieval.

  8. Exit the pod shell: 
    exit

C. Retrieve DDA

  1. Copy DDA from pod to server tmp: 
    kubectl cp <POD-NAME>:/tmp/DDA/<DDA-FILENAME> /tmp/<DDA-FILENAME>
  2. Transfer DDA from server to local Downloads: 
    scp cont12986:/tmp/<DDA-FILENAME> ~/Downloads/
  3. Attach the DDA file to the JIRA ticket and share a confirmation email indicating the DDO is processed successfully.

Notes & Tips

Aliases and contexts

i Commands like pods and logs may be shell aliases; use explicit kubectl equivalents and verify current context when aliases are unavailable.

Collapsible help

i The details/summary elements are native, accessible toggles when summaries have concise, descriptive labels per MDN guidance.

Sticky navigation

i The left TOC uses CSS position: sticky and a top offset, so it remains visible while scrolling within its container.